[postcss-plugin] Add @layer and polyfill support via @csstools/postcss-cascade-layers#1072
[postcss-plugin] Add @layer and polyfill support via @csstools/postcss-cascade-layers#1072jeongminsang wants to merge 7 commits intofacebook:mainfrom
Conversation
|
Hi @jeongminsang! Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at [email protected]. Thanks! |
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks! |
necolas
left a comment
There was a problem hiding this comment.
Thanks for giving this a try.
The layers polyfill should be part of the babel-plugin processStylexRules method. The unit tests for that API should also be updated to snapshot the output from the 3 different options. The other packages like the CLI and postcss-plugin can then call into processStylexRules and pass an options object instead of the current boolean.
|
@necolas, |
What changed / motivation ?
This update refactors the useCSSLayers option to streamline the implementation of CSS layer polyfilling. We're replacing our custom, internally handled polyfill with the robust and well-maintained @csstools/postcss-cascade-layers library. This ensures a more compliant and robust solution for handling CSS layer specificity.
Linked PR/Issues
Fixes #1062
Additional Context
useCSSLayers Option Refactoring
The previously self-implemented polyfill logic has been removed:
The polyfill functionality is now powered by @csstools/postcss-cascade-layers, ensuring a more robust and compliant solution: